Hello @daniel-beck , I need your help on this one. I'm currently migrating "Artifactory Users" branch into its own pipeline, and the job fails when uploading the report into the bucket with the error ERROR: The specified blob already exists. (ref. https://infra.ci.jenkins.io/job/reports/job/artifactory-users-report/job/PR-37/30/execution/node/29/log/).

As per https://github.com/jenkins-infra/infra-reports#artifactory-users-report, I understand that the json report should be consumed when the RPU jobs runs (https://github.com/jenkins-infra/repository-permissions-updater/blob/master/src/main/groovy/io/jenkins/infra/repository_permissions_updater/KnownUsers.groovy).

But RPU seems to run every 3 hours (as per https://github.com/jenkins-infra/repository-permissions-updater/blob/master/Jenkinsfile#L17) while the actual infra-reports runs once per hour (https://github.com/jenkins-infra/infra-reports/blob/main/Jenkinsfile#L6) => I understand that the artifactory-report would be uploaded 2-3 times between 2 builds of RPU.
What did I miss exactly that prevent the upload to happen?

(edit) nevermind: the error is related to the az command line , which version changed. Just confirmed it by using the old version and it works.

OK, seems good to me. I need a careful review (what did I miss because for sure I missed something) + 24h to ensure that the reports are generated repeatly as expected.

@lemeurherve spaces fixed on Jenkinsfiles

@dduportal WDYT about restoring the Dockerfile(s) so users can locally run these scripts without having to install their dependencies?

@dduportal WDYT about restoring the Dockerfile(s) so users can locally run these scripts without having to install their dependencies?

They should use the image jenkinsciinfra/helmfile instead. Is it ok if I add this to the readme?

@lemeurherve README updated + stage name updated so the github checks are easier to catch.

Closing the PR to avoid messing up with current trusted.ci. Will be reopen with fixes

Hello @zbynek @daniel-beck @NotMyFault @timja @lemeurherve

I've reopen the PR with the following notable changes (after the issues which caused jenkins-infra/plugin-site#1150):

• Rolling back using jq version 1.5, as the alpine linux version is 1.6
• Do not enable cron rebuild when not on the principal branch
• Use a different report name when not on the principal branch (to allow comparing). Please note that there is no garbage colelcting on this one.

Update:

• The report generated on the last version does not have the jq prepended which looks better. Reports looks valid syntaxically, but I reall need help to check it.
• WDYT about disabling the publication step to the bucket when not on the principal branch? That would avoid the bucket being messy with a bunch of "*-PR-XX.json" files. Validation of the generated reports would be done through the archived artifact in PRs

WDYT about disabling the publication step to the bucket when not on the principal branch?

I'd say go for it.

Artifacts based comparison seems preferable.

Proceeding to merge + disabling former job in trusted.ci.
Gotta monitor the generated report and the RPUs runs all day long and tomorrow.